fix: Add support for Japanese slash date without year #16
+21
−4
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Fixes a bug where year-less, slash-separated dates (e.g.,
6/20(木)) failed to parse correctly when thelang: "ja"option was active.Details
addYearToDateTextfunction to prioritize generic date formats over language-specific ones.2025年6/20(木), which broke the date parser./) and dash (-) formats are handled first, guaranteeing correct year supplementation.Behavior Before vs. After
With options
{ useCurrentYearIfMissing: true, currentYear: 2025, lang: "ja" }:Before
"6/20(木)"After
"6/20(木)"6/20(木) mismatch weekday.\n6/20(木) => 6/20(金)Background
This patch addresses an edge case not covered in the initial implementation of the
useCurrentYearIfMissingoption (see #14), improving the rule's reliability for common date formats in Japanese.